-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Migrate to Express [*****] #7877
Closed
Closed
Changes from 21 commits
Commits
Show all changes
25 commits
Select commit
Hold shift + click to select a range
6d72fd6
Begin to replace scoutcamp with express
paulmelnikow 7c071e3
Core tests passing
paulmelnikow 6e6cec9
Move one test
paulmelnikow c3097aa
Fix / remove obsolete tests
paulmelnikow aeebfaa
Renames
paulmelnikow cf6b5b1
Remove obsolete code
paulmelnikow 15043df
Remove more obsolete code
paulmelnikow 903bef2
Finish rename
paulmelnikow aa046cb
Fixes
paulmelnikow be9d490
More tests passing
paulmelnikow 8cbc8cb
More tests passing
paulmelnikow e8f59a2
More fixes
paulmelnikow 6d77534
Progress / cleanup
paulmelnikow b4f7ec3
Update integration tests
paulmelnikow 00df3e1
Clean diff
paulmelnikow b19ca20
Update docs and suggest test
paulmelnikow 78b886c
Merge branch 'master' into express
paulmelnikow 18c76e3
Clean up acceptor test
paulmelnikow 9d6b3e0
Clean lint
paulmelnikow 25ab480
Clean up makeBadge tests
paulmelnikow 416ef39
Don't alias `this`
paulmelnikow 1761aab
Wee bit of cleanup
paulmelnikow fc13e8e
Merge branch 'master' into express
paulmelnikow ca6ae88
Tweak style
paulmelnikow fc68b88
Merge branch 'master' into express
paulmelnikow File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've argued before that this functionality doesn't belong in the badge library as the particular JSON schema we generate here (with
name
andvalue
) is a legacy quirk of shields.io, and not something we particularly want users to replace elsewhere. For the moment I went ahead and moved this functionality to the server. It's now handled bymakeJsonBadge()
which is invoked from a conditional in the request handler inbase.js
.If we keep this we'll probably want to add normalizeColor to the package's public interface, or alternatively a
normalizeBadgeData()
function, and then we could start dogfooding the publicmakeBadge()
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't read over the code for this bit at all yet. I agree with the objective. Has anything significant has changed since #4980 in terms of the implementation, specifically #4980 (comment) ? I will have a look through it. If a slightly different configuration of not eating our own dogfood is necessary to get off scoutcamp, this shouldn't be a blocker but until we do #4947 and #4949 I suspect all we can really do is move from one undesirable implementation to another. I do accept #4947 and #4949 have been open for 2 years and none of us are actively working on them.
As a note, we may want to consider documenting it as a non-BC change for badge-maker, even though
format='json'
is undocumented. The next badge-maker will be a major release anyway due to dropping node 10.