What happens if I specify a src and an inline config?

In amp-story-share:

getInlineConfig_() {
    const bookend = this.storyEl.querySelector('amp-story-bookend');
    const inlineConfig = bookend.querySelector('script');

   ...
}

I think we should avoid these hard dependencies. Unfortunately here, I don't know how we can keep amp-story-share / amp-story-bookend communication going through the store service. There are cases where we don't want to load the bookend configuration before actually preloading the bookend (mobile version on a phone that supports native sharing doesn't need to know about the share providers).

Maybe we should refactor the request-service to support this feature, since it already queries the DOM for amp-story-bookend anyway.

src would have the priority over the inline config, since it might be more fresh? Having an inline config to make things easier, or as a fallback, is a really cool feature.

What happens if I specify a src and an inline config?

src would have the priority over the inline config, since it might be more fresh? Having an inline config to make things easier, or as a fallback, is a really cool feature.

I was thinking that if both are specified then we'd want to prioritize the inline config so that we avoid doing unnecessary XHR's. But what you mention sounds like a better UX/devX.

Maybe we should refactor the request-service to support this feature, since it already queries the DOM for amp-story-bookend anyway.

Yeah, now that we think of the inline config as a fallback we can refactor the request service to get the inline config as a fallback when there's no src specified.

I'll update the PR with these points taken into consideration.

/cc @honeybadgerdontcare @Gregable for validation