tequ
It seems to have been fixed.
It seems to have been fixed.
Also, the following sections outside of the default function cannot be translated. ```ts export const frontmatter = { seo: { title: 'Dev Tools', description: "Use these tools to explore, build,...
> In other PR, I suggested adding a [check](https://github.com/XRPLF/rippled/pull/4838#issuecomment-1838855814) so that NFTokenModify would fail if there is any outstanding offers. This is to prevent the issuer from changing the URI...
> BTW, the "Context of change" section linked to the XLS20 proposal, I think you meant to link to this one [XRPLF/XRPL-Standards#130](https://github.com/XRPLF/XRPL-Standards/discussions/130) good catch, fixed!
@scottschurr Thanks for the review. I fully agree with your suggestions and have cherry-picked all three commits.
> I suggest holding off on merging this PR until the [Clio counterpart](https://github.com/XRPLF/clio/pull/1525) is also approved. While this isn't standard practice, the NFT functionality is in a unique position where...
ready to merge👍
> @tequdev it looks like this code doesn't check for invalid flags - can that be added in a separate PR? Nice catch! You can check the changes in this...
It seems that most situations can be handled with that script. but isn't Balance to be 0 in a situation where an AMMDelete transaction could happen?