-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Some wording improvements, clarifications, etc. #10180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Reason: I think the docs should show a *minimal* working example. The user needs to customize it anyway, so coming up with a bells-and-whistles solution only makes the entire process look more complicated than it is. I entered the "Add new tag" link into the HTML directly, cause I couldn't see any benefit of having it added dynamically. I didn't update the JSFiddle though. I'm not finished yet - this code might break the JavaScript further down the page (the "remove tag" link)
Question: I'm not sure about this line: newForm = newForm.replace(/__name__label__/g, index); I can never see And I don't even see what its point would have been. Put the index inside the label? Why? |
Started with some minor corrections, ended up with a major reorganization ;-) I'm done for now, please merge. |
Hey @ThomasLandauer! This is awesome! Sorry for the delay - these big changes are hard to review. Do you have a test repository where you built the code? We really need to code through this to make sure everything still works properly. Cheers! |
No, I entered everything on GitHub's website. But I didn't change the actual code that much - just moved stuff around ;-) |
Ah, ok! Were there any parts of the code that you changed in any significant way? The diff in these re-org PR's is hard to check (I'm the king of massively re-organizing stuff, so that's not a complaint about your PR!) |
To be honest: I don't really remember :-( But I guess not, I think I just explained things better. |
I need this functionality for another project in a few days. If you could merge it till then, I could double-check if everything's all right. But I'd need it on the real website - can't work with this GitHub "preview" ;-) |
Do you want me to set up a repository as explained at https://symfony.com/doc/current/contributing/code/reproducer.html ? |
Hi @ThomasLandauer 👋
That would be cool! |
Hey Thomas 😊 We really appreciate your work, but the 2.8 branch isn’t maintained anymore. Please rebase on 3.4 branch first, most of the things are already fixed and we don’t want to waste your time. Anyway thanks for your help 👌🏻 Cheers, Oskar |
See https://github.com/ThomasLandauer/symfony-docs_pr_10180 Sorry, I don't know how to rebase :-( So please help me out now, I spent hours for this! |
Suggestion: Separate headings for all possible relationship types. Right now, the page contains too many "In case you have A, you need to pay attention to B, etc.". In this phase (i.e. when the user thinks about setting up an "add" button"), the database model is fixed anyway! Nobody will say "Well, if it's easier to get the button, let's change the relationship type!" So wouldn't it be better to take the relationship type as granted and give a step-by-step tutorial for each type? |
Hi Thomas 👋 I am sorry, but I will to close here, Thank you for your understanding! Cheers, Oskar |
July 30:
November 14:
|
Hi Thomas, I am sorry but you offered todo this and I just wanted to say "yes that would be great and more easy for the one who will help you", so I saw my position more or less to be a moderator on topics/issues/pull requests. Sorry for being not clear enough and you thought, that I could help you out. My recommendation is still to provide small pull requests, your last one was merged really quickly (grammar, typo IIRC). Cheers, Oskar |
I don't know who of you is in charge of what! This isn't documented anywhere (or is it?) So if somebody tells me to do something, I usually do it. Oskar, I can't know which role you're playing in the entire game. What I'm blaming you, personally, was to tell me to put more work into this, at a time when it was (I'm 99% sure about this) already futile. The same is eventually going to happen to #11222 and #11223 :-( Small PR's: |
Eventually.. yes.. 😞
Sorry but many users are very very happy with the Symfony documentation, so personally I am convinced, that we are doing good work. And please remember we are doing all this beside our main jobs ❗️ without any payment ❗️ in our freetime ❗️ Have a good day ☀️ |
No description provided.