Skip to content

Conversation

@JFWooten4
Copy link
Contributor

@JFWooten4 JFWooten4 commented Sep 22, 2025

Same as JFWooten4#9 but with edit perms

John Wooten and others added 30 commits June 20, 2024 07:55
- Starlight active, details confirmed with SDF at https://discord.com/channels/897514728459468821/907476473739354153/1259478260220301362

- Searching for src on global consensus data packet propogation for relevance in random submisison delay

- Need to get hard reference for Protocol 20 one-txn-per-ledger limit
- First time working with this in mdx, pretty nice
I understand there's more to do in `docs\data\READ_FIRST.md`, but I'm just not going to deal with that until stellar#1044
This way only runs the Husky pre-commit if you have yarn installed, which should help with stellar#1044 compatability, given those with write access can quickly (via bot?) run the formatting. i had a lot of problems with this three weeks ago when editing on an offline laptop that didn't have all the dependencies involved. Even though I was going to take care of the nuances on this main desktop here, I couldn't synch up my work to the branch, and thus it was hard to manually override the git commit checks.
Husky changes here should respect stellar#96 given the autochecks run formatter and fail if not prettier at `check MDX` step
Also removes  a lot of redundant language from the intent of d5ff964
also bypass the check if yarn run fails for reasons unrelated to file issues like Node version mismatch or corrupt environment
This gets into how deeply we want  to epxlain paths in stellar#1545
This cleans up the wording around stellar#1061 without reviewing the pages we notify users about `consistency`.

I think a better long-term solution is a "Consistency" flag added to the affected endpoint pages. This could be a simple button akin to the "Supports Streaming" info box. However, even that seems a verbose solution which would also do well to exist as a simple button (akin to  ledgerStorage) > two sentences.
@JFWooten4
Copy link
Contributor Author

JFWooten4 commented Sep 22, 2025

for some reason these are all the same conflicts as #723, so I'm going to try a merge update there before doing a command-line merge --no-ff for Elliot's work (which should then have a clean comparison)

mirrored due to wrong PR base branch

@JFWooten4
Copy link
Contributor Author

wrong org, meant personal

@JFWooten4 JFWooten4 closed this Sep 22, 2025
@JFWooten4 JFWooten4 deleted the ElliotFriend-refresh-classic-guides branch September 22, 2025 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant