Fixes and refactors #9
Open
Conversation
This file contains hidden or 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
|
I realized that it may be necessary (I've already added it to the function schema) to have an optional property to specify whether the function has optional parameters. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request includes a small change to the
web/src/pages/[func].astrofile. It updates thefuncPairlink to prepend a forward slash (/), ensuring the link resolves correctly as a relative path.In the previous code, when clicking on the pair function, the user was redirected to a non-existent page but the URL was displayed as a page relative to the current page where the user was.
For example, I was on the
/setElementHealthpage, when I tried to access the pair function I went to/setElementHealth/getElementHealth.